get_properties

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

With no annotations, the description states it's a read operation, implying no side effects. However, it lacks details on permissions, error handling, or performance implications. Basic transparency is present but not comprehensive.

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, concise and front-loaded. The use of 'etc.' is slightly informal but does not significantly harm conciseness.

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 no output schema and no annotations, the description fails to explain the return format or any additional context. For a tool with one parameter, it leaves many questions unanswered for a new user.

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?

Schema description coverage is 0%, and the description adds no explanation for the doc_id parameter. The parameter name is common but not elaborated, leaving ambiguity about what constitutes a valid document ID.

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 'Read' and the resource 'document properties', and gives examples (Title, Author, etc.). It distinguishes from sibling 'set_properties' by being read-only, but 'etc.' is vague and doesn't specify the full scope of properties.

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 implies when to use (reading properties) but provides no explicit guidance on alternatives or when not to use. No mention of sibling 'set_properties' or 'get_info' for different needs.

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