get_my_agent_info

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

No annotations are provided, so the description fully covers behavioral traits. It declares it is 'Read-only. Does not modify any data.' and explains it returns private details not available through get_agent_info. It also mentions the use of the AVP_AGENT_NAME environment variable.

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 well-structured and front-loaded with the core purpose. Each sentence contributes unique value: purpose, usage guidelines, exclusions, parameter clarification, safety, and return format. No redundant or irrelevant information.

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?

Despite the tool having no parameters and an existing output schema, the description provides complete context: purpose, when to use, when not, safety (read-only), implicit configuration, and return structure sample. This fully compensates for the lack of annotations.

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?

There are no parameters in the schema, but the description adds value by clarifying that it uses an implicit agent configuration via the AVP_AGENT_NAME environment variable, which goes beyond the schema's empty requirements.

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 verb ('Get'), the resource ('YOUR agent's DID, registration status, and reputation'), and the scope ('locally configured agent only'). It distinguishes from siblings by noting it is not for looking up other agents, unlike get_agent_info.

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 states when to call ('before calling submit_attestation or publish_agent_card') and when not to use it ('NOT for looking up other agents'). Provides named alternatives: get_agent_info(did) and check_reputation(did).

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