whoami

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses essentially nothing about side effects, permissions, or whether the call is safe/non-mutating. For a trivial zero-arg lookup this is a modest gap, but identity tools can leak auth/instance context that is worth calling out.

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?

It is a single short sentence with no padding, which is good, but it is under-specified rather than genuinely concise — the fragment lacks a subject/verb and spends its one clause on the return value instead of the action.

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?

With no output schema and no annotations, the description does at least indicate what the call yields (account and instance), which is the essential payload. However it omits the return format and any indication of when the result matters, leaving it minimally adequate for a diagnostic tool.

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, so the baseline is 4. There are no arguments whose semantics the description could clarify or confuse.

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 names the resource it exposes (the Canvas account and instance) but is a noun-phrase fragment with no verb, so it reads as a label rather than a statement of what the tool does. An agent can infer it returns identity/connection info, but the purpose is only implied. It is distinguishable from all grading-related siblings, which helps.

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?

There is no when-to-use guidance, no mention that it takes no arguments, and no comparison to alternatives. The only guidance is implicit from the name 'whoami'. Nothing tells the agent whether this is a setup/verification step or a routine call.

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