get_my_profile

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotation readOnlyHint=true already signals the operation is safe. The description adds valuable context by specifying that only the caller's own record is returned, not anyone else's, and enumerates the returned fields (user ID, name, login ID). This goes beyond the annotation and clarifies the tool's behavioral scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exceptionally concise: two sentences that front-load the action and result, followed by the use case and scope. Every word adds value, with no redundancy or fluff. This is a model of efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no inputs, no output schema, read-only), the description is fully complete. It states the returned data, the privacy boundary, and the intended use case. There are no gaps left for the agent to infer, making it sufficient for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, and the schema coverage is 100% (empty properties). The baseline score for 0 params is 4, and the description appropriately focuses on the output and use case rather than param details, which are nonexistent. No additional parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches the caller's own Canvas identity (user ID, name, login ID). The verb 'Get' and resource 'my profile' are specific and distinct from all sibling tools, which focus on courses, assignments, or messages. It unambiguously answers 'who am I?'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use it: 'useful when a tool needs your Canvas user ID or NetID.' It also clarifies scope ('Reports only your own record'), which prevents misuse for fetching others. Though it doesn't name alternative tools, this is unnecessary given no sibling offers similar functionality, so the guidance is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.