Get trusted Agent DNA

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

The annotation already declares readOnlyHint and destructiveHint, and the description redundantly says 'Read-only'. It adds the context that data comes from 'server-side trusted state', which is mildly informative. However, it doesn't disclose any other traits like required permissions, error behavior, or what happens if agentId is invalid.

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 a single sentence plus 'Read-only', which is concise and front-loaded with the primary function. No unnecessary information is included.

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?

For a one-parameter read-only tool, the description is adequate but leaves gaps: no output schema means the return format is unspecified, and the term 'Agent DNA' is not explained. Given the lack of usage guidance and parameter clarification, the description is minimally complete but not thorough.

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 schema has no description for agentId, and the tool description also fails to explain what agentId represents or how it should be formatted. With 0% schema description coverage, the description needed to compensate but did not, leaving the parameter ambiguous.

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 states a clear verb ('Return') and a specific resource ('trusted Agent DNA state and fingerprint information'), distinguishing it from generic operations. However, it doesn't explicitly differentiate from siblings like get_authority or get_mandate, and 'Agent DNA' is not defined in context.

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 provides no guidance on when to use this tool versus its siblings. It only states what it does and that it's read-only, without mentioning conditions, alternatives, or exclusions. The agent must infer usage from the title and resource name.

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