get_abstract

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

With no annotations, the description must disclose behavioral traits but only says 'Get the abstract'. It does not mention that this is a read-only operation, what permissions are needed, or what the return value looks like. The input is an opaque 'RFCDocument' object.

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 very short—one sentence—which is concise. However, it is under-specified for a tool with a complex input parameter and no output schema, so conciseness becomes a trade-off with completeness.

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 lack of output schema, the description should explain what the abstract is (e.g., string, object) and how it relates to the input document. It does not, leaving the agent to guess the return format. Sibling tools imply an RFC context, but the description alone is insufficient.

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 describes the parameter 'document' as 'RFCDocument', which is purely a type name and adds no semantic meaning. The description repeats this without adding details about the document structure or how to obtain it. The parameter is a nested object with no exposed properties.

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 'Get the abstract of an RFC document', specifying the verb and resource. It distinguishes this tool from siblings like 'set_abstract' and 'get_document'. However, it does not clarify how the abstract is identified or what the input 'document' object represents.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_document' or 'get_section_by_title'. The description lacks context on prerequisites or preferences.

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