get_extension_status

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

No annotations provided, but description explains return fields and their meanings (e.g., IsRegistered=true=phone connected). Even without annotations, it's transparent about what the tool returns.

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?

Two concise sentences: first provides usage examples, second explains return fields and alternatives. Front-loaded with essential information, no waste.

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 one parameter and no output schema, the description fully explains return fields and provides context for related tools. Complete for a simple status lookup 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?

Single parameter 'extension' with schema description 'Extension number, e.g. '101''. Schema coverage is 100%, so baseline is 3. Description adds example usage but no extra semantic detail beyond the schema.

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?

Clearly states the tool returns extension status with specific fields (Number, DisplayName, IsRegistered, etc.) and gives example queries. Distinguishes from sibling tools like get_user and find_users.

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?

Explicitly says when to use (user asks about extension status like 'is extension 101 online?') and when not (for full user details use get_user, for searching by name use find_users).

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